jextract/jni: Support optional tuple return values 2#723
Open
sidepelican wants to merge 7 commits intoswiftlang:mainfrom
Open
jextract/jni: Support optional tuple return values 2#723sidepelican wants to merge 7 commits intoswiftlang:mainfrom
sidepelican wants to merge 7 commits intoswiftlang:mainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is an improved version of #720.
Currently, code generation is skipped when an optional tuple is used as a return value.
This PR addresses this limitation.
Support for optional tuples as parameters remains out of scope for this PR.
Thanks to the architectural improvements in #722, I'm now able to handle these tuples properly without the need for any workarounds.